Systems and methods for digitization services

ABSTRACT

Embodiments relate to systems and processes for digital document services, having at least a processor and a non-transient data memory storage, the data memory storage containing machine-readable instructions for execution by the processor, the machine-readable instructions configured to, when executed by the processor, provide a document service. The document service can extract data from a plurality of source systems; load and store the data at a data hub implemented by a non-transient data store; receive a request to generate a document package at the data hub, the request indicating a target unit; generate and store the document package using a subset of data from the data at the data hub, the document package having at least one electronic signature request; detect a signature event at the data hub; and transmit the document package to the target unit.

CROSS REFERENCE TO RELATED APPLICATION

This application claims priority to U.S. Provisional Application No.62/700,394 entitled SYSTEMS AND METHODS FOR DIGITIZATION SERVICES, thecontents of which is hereby incorporated by reference. This applicationrelates to U.S. application Ser. No. 16/517,253 entitled SYSTEMS ANDMETHODS FOR DATA STORAGE AND PROCESSING, the contents of which is herebyincorporated by reference.

FIELD

The present disclosure generally relates to the field of data storagesystems and processing.

INTRODUCTION

A full-service financial service institution depends heavily on the useof technology to serve customers with a wide range of products andservices. In addition, technology is used to meet stringent riskmanagement and regulatory compliance.

An organization with a long history typically has adopted a myriad rangeof technologies from legacy platforms like mainframe to moderncapabilities like mobile and analytic applications. An organizationmight have a large set of applications (many hundreds) throughacquisition and integration.

To continue to deliver differentiating customer experience andtransformation to keep pace or leap-frog competitors, both traditionaland disruptive ones, an institution needs to be able to effectively andefficiently integrate the complex and diverse set of applications. Anintegrated enterprise not only forms the foundational capability todeliver any product and service across different channels, it alsoenables the ability to identify events and generates actionable insightsto become an intelligent institution.

SUMMARY

Embodiments described herein relate to digitization and documentmanagement.

For example, this can involve capturing or scanning physical documentsand performing recognition operations (to capture data form thedocument) for conversion into electronic documents to be properlycataloged and filed into the enterprise document repository forsubsequent search and retrieval. In addition, documents associated witha specific business function (e.g., mortgage application may requiremultiple different documents) are automated tracked as a documentpackage throughout its lifecycle, which is often integrated through abusiness process management (BPM) application that forms a repeatableand reusable business process pattern. This is an example businessprocess pattern that can be used for Branch Scanning. Another exampleprocess pattern can be for Retail Branch service and productonboarding/account open process. The system can integrate the branchscanners which are informed by the document tracking services (builtwithin a storage integration layer) to scan a document packagedetermined by specific products/services onboarding BPM process. Suchprocess has been reused for Wealth Management branch business. Theprocesses can also be extended for business and commercial bankingbranch/office use case as well.

Systems for digitization and document management can connect with adigital library to access and update document data.

In an aspect, embodiments described herein provide a system for digitaldocument services, comprising at least a processor and a non-transientdata memory storage, the data memory storage containing machine-readableinstructions for execution by the processor, the machine-readableinstructions configured to, when executed by the processor, provide adocument service configured to: load and store data from a plurality ofsource systems at a data hub implemented by a non-transient data store;define and store, at the data hub, process pattern for digitization ofdocuments, the process pattern indicating document types; receive arequest to generate a document package at the data hub, the requestindicating a target unit, the request linked to the process pattern;generate and store, at the data hub, the document package using a subsetof data from the data at the data hub and physical documents convertedto electronic format according to the process pattern, the documentpackage stored at the data hub for subsequent search and retrieval; andtransmit the document package to the target unit.

In some embodiments, the document package is associated with a documentpackage identifier, wherein the document services is configured tomonitor the document package at the data hub, detect a document changenotification, and store the change notification in association with thedocument package identifier as part of an audit log.

In some embodiments, the document services is configured to receive andstore a modified version of the document package containing at least oneelectronic signature in response to at least one electronic signaturerequest.

In some embodiments, the document services is configured to assign thedocument package to a user identifier having an access role, whereinprior to transmission, the document services is configured to check theaccess role and the target unit.

In some embodiments, the document package has at least one electronicsignature request and wherein the processor can detect a signature eventat the data hub and capture data from the signature event for storage aspart of the document package.

In some embodiments, the document services comprises an electronicsignature event listener to process the electronic signature event inreal-time.

In some embodiments, the document services comprises an electronicsignature event handler to receive the electronic signature events inreal-time from the electronic signature event listener.

In some embodiments, the process pattern is linked to a businessfunction, domain or application.

In some embodiments, the process pattern indicates a number of requireddocuments for the document package.

In some embodiments, the process pattern indicates a type of requireddocument for the document package.

In some embodiments, the processor integrates with one or more scannersto capture scanner data for the document package, the one or morescanners capturing the physical documents.

In accordance with an aspect, there is provided a system for digitaldocument services, comprising at least a processor and a non-transientdata memory storage, the data memory storage containing machine-readableinstructions for execution by the processor, the machine-readableinstructions configured to, when executed by the processor, provide adocument service configured to: extract data from a plurality of sourcesystems; load and store the data at a data hub implemented by anon-transient data store; receive a request to generate a documentpackage at the data hub, the request indicating a target unit; generateand store the document package using a subset of data from the data atthe data hub, the document package having at least one electronicsignature request; detect a signature event at the data hub; andtransmit the document package to the target unit.

In various further aspects, the disclosure provides correspondingsystems and devices, and logic structures such as machine-executablecoded instruction sets for implementing such systems, devices, andmethods.

In this respect, before explaining at least one embodiment in detail, itis to be understood that the embodiments are not limited in applicationto the details of construction and to the arrangements of the componentsset forth in the following description or illustrated in the drawings.Also, it is to be understood that the phraseology and terminologyemployed herein are for the purpose of description and should not beregarded as limiting.

Many further features and combinations thereof concerning embodimentsdescribed herein will appear to those skilled in the art following areading of the instant disclosure.

DESCRIPTION OF THE FIGURES

In the figures, embodiments are illustrated by way of example. It is tobe expressly understood that the description and figures are only forthe purpose of illustration and as an aid to understanding.

Embodiments will now be described, by way of example only, withreference to the attached figures, wherein in the figures:

FIG. 1A illustrates a system architecture diagram of a proprietaryInformation Delivery Platform (IDP) in accordance with one embodiment.

FIG. 1B is a view of components of a data storage and processing systemincluding IDP.

FIG. 2 illustrates a schematic diagram of a digitization serviceplatform as part of the IDP of FIG. 2 according to some embodiments.

FIG. 3 illustrates a schematic diagram of a digitization serviceplatform according to some embodiments.

FIG. 4 illustrates a schematic diagram of a digitization serviceplatform according to some embodiments.

FIG. 5 illustrates a schematic diagram of a digitization serviceplatform according to some embodiments.

FIG. 6 illustrates a schematic diagram of a digitization serviceplatform according to some embodiments.

FIG. 7 illustrates a schematic diagram of a digitization serviceplatform according to some embodiments.

FIG. 8 illustrates a schematic diagram of a digitization serviceplatform according to some embodiments.

FIG. 9 illustrates a schematic diagram of a digitization serviceplatform according to some embodiments.

FIG. 10 illustrates a schematic diagram of a digitization serviceplatform according to some embodiments.

FIG. 11 illustrates a flow diagram of a digitization service platformaccording to some embodiments.

FIG. 12 illustrates a flow diagram of a digitization service platformaccording to some embodiments.

FIG. 13 illustrates a flow diagram of a digitization service platformaccording to some embodiments.

FIG. 14 illustrates a schematic diagram of a digitization serviceplatform according to some embodiments.

FIG. 15 illustrates a schematic diagram of a digitization serviceplatform according to some embodiments.

FIG. 16 illustrates a schematic diagram of a digitization serviceplatform according to some embodiments.

FIG. 17 illustrates an example interface of a digitization serviceplatform according to some embodiments.

FIG. 18 illustrates a schematic diagram of a digitization serviceplatform according to some embodiments.

FIG. 19 illustrates a schematic diagram of a digitization serviceplatform according to some embodiments.

FIG. 20 illustrates a schematic diagram of a digitization serviceplatform according to some embodiments.

FIG. 21 illustrates a schematic diagram of a digitization serviceplatform according to some embodiments.

FIG. 22 illustrates a schematic diagram of a digitization serviceplatform according to some embodiments.

FIG. 23 illustrates a schematic diagram of a digitization serviceplatform according to some embodiments.

FIG. 24 illustrates a schematic diagram of an example architecture of adigitization service platform according to some embodiments.

FIG. 25 illustrates a schematic diagram of a digitization serviceplatform according to some embodiments.

FIG. 26 illustrates a schematic diagram of a digitization serviceplatform according to some embodiments.

FIG. 27 illustrates a flow diagram of a digitization service platformaccording to some embodiments.

FIG. 28 illustrates a schematic diagram of an example architecture of adigitization service platform according to some embodiments.

DETAILED DESCRIPTION

Embodiments of methods, systems, and apparatus are described throughreference to the drawings.

The following discussion provides many example embodiments of theinventive subject matter. Although each embodiment represents a singlecombination of inventive elements, the inventive subject matter isconsidered to include all possible combinations of the disclosedelements. Thus if one embodiment comprises elements A, B, and C, and asecond embodiment comprises elements B and D, then the inventive subjectmatter is also considered to include other remaining combinations of A,B, C, or D, even if not explicitly disclosed.

The embodiments of the devices, systems and methods described herein maybe implemented in a combination of both hardware and software. Theseembodiments may be implemented on programmable computers, each computerincluding at least one processor, a data storage system (includingvolatile memory or non-volatile memory or other data storage elements ora combination thereof), and at least one communication interface.

Within an enterprise data warehouse, there may be large volumes of databeing ingested and stored; computational demands may also be high forextracting, transforming or otherwise processing the volumes of datainto end target databases or end appliances. With traditional ETLtechniques, there exists a number of pain points: “data silos”, whichrefer to data that is under control of one group or application andisolated from the rest of the organization may be common, and there maybe need for replication of large volumes of data between the variousappliances. In addition, computing and storage capacity are inherentlycoupled, and cannot be independently scaled. Data access control andsecurity may be negatively affected.

The financial cost of data aggregation and consumption with currenttechnology may be high, and meeting demand may become increasinglytechnically challenging.

Network bandwidth may also become a significant constraint for datacommunication between an enterprise data system and external systems, aswell as in/out of the landing zone for batch data transmission for theenterprise data system.

In addition, capturing and maintaining accurate data lineage may also bechallenging under the traditional approach.

There may be no “balance and control” or enterprise-level reconciliationpatterns or models for data stored within a traditional enterprise datasystem. This may be the case if the enterprise data system serves as abook-of-reference and not a book-of-record. However, there is growingneed for enterprise reconciliation/balance and control capabilities andpatterns.

Improving ease of understanding of the data glossary and relationshipbetween data/sources is needed to support self-serve data scienceinitiatives.

The Financial Services Industry is a data driven industry. The scope,quality, cost, performance and freshness of data that has been “goodenough” in the past is no longer good enough. Many critical bankprocesses require low cost, easy to access, reliable and consistentdata. These process include but are not limited to: Anti MoneyLaundering Compliance, Regulatory and Compliance Reporting, RiskManagement, Customer Insights, Sales Performance Management and ChannelOptimization.

The Information Delivery Platform described in the embodiments hereinincorporates new technology and a new operating model that optimizes theaccountabilities for data quality and a simplified approach toinformation management. This platform may provide information managementcapability to meet the rapidly increasing demand for low cost, easy toaccess, reliable and consistent data.

Referring now to FIG. 1A, which illustrates a system architecturediagram of an example Information Delivery Platform (IDP) 2100 withChannels 2300, Product Systems 2400 a, Corporate Systems 2400 b and T&O(Technology and Operation) Systems 2400 c.

In an example embodiment, IDP 2100 is a data aggregation, processing,and analytics environment, combining multiple sources of data into asingle organization-wide repository, and providing fast andcost-effective access to data.

In the present application, as an example, the organization is a bank.However, it should be appreciated that the organization can be any typeof organization or company that requires storage and processing of datafor daily operations. For example, the organization can be a governmententity, a law firm, a school, a store, or a restaurant, and so on.

IDP 2100 provides more data in less time. It provides users with a highperformance platform for processing queries. It has built in dataquality management, high availability and disaster recovery. Itsinnovative operating model provides subscriber businesses a direct CIOaccountability to ensure their specific needs are met. It may providethe opportunity to eliminate data sprawl by eliminating the motivationsto create redundant and overlapping data marts. It may provide thefollowing benefits: CIO accountability model means conversations aboutsourcing data, its content and it's quality take place directly betweenthe owners of the source systems and the consumers of the data; highperformance, cost efficient staging platform means improved queryperformance and lower costs for accumulating low level detail data; dataquality management means problems in the source data are identifiedearly and actively managed; consumer driven data model means theintegrated database structures are presented in simple, businessfriendly terminology; and provides for self-serve data usage.

IDP 2100 is a shared information management component of theAnalytical/Data Hub that will provision well managed data to meetmultiple reporting and analytical requirements quickly and efficiently.Its innovative operating model leverages the strengths of allstakeholders and eliminates unnecessary hand offs. It is built from theground up to meet the requirements of regulators and business processthat demand on-going demonstration of data quality management and proofthat the data is an accurate and complete representation of reality. Itpresents data to the business community using industry and bankterminology. It will provide the opportunity to eliminate data sprawl byeliminating the motivations to create redundant and overlapping data. Itmay provide robust, highly resilient infrastructure, DR (DisasterRecovery), high performance as most queries and loads run in a fractionof the time of existing platforms, easy tracking of data assets undermanagement, data stewardship and data governance, data qualitymanagement and reporting capability, and data in cross applicationintegrated (L2) model.

In an example embodiment, central data hub 3000 includes IDP 2100. Inone embodiment, the IDP 2100 may include a scalable data store (alsoreferred to as a “data lake”), which may collect and store massiveamounts of data for long periods of time. The data stored may bestructured, semi-structured, unstructured, or time-sensitive data (e.g.events, etc.). A central aggregation and distribution point (“book ofreference”) may be generated for all book-of-record data within thebank, which provides consistent and efficient access to reference data.Both raw and processed data within the data lake may be available forconsumption; powering analytics; machine learning; consumer-specificdata accessible via batch, SQL, streaming, native Hadoop APIs. Linearscalability of data is also provided.

In some embodiments, IDP 2100 is connected to channel services 2300through connector grid 2110 a and connected to product systems 2400 a,corporate systems 2400 b and T&O systems 2400 c through connector grids2110 b and 2110 c.

Channel services 2300 may include internal or external interfacesadapted for different service groups, such as Point-of-Sale (POS)terminals, watch interfaces, mobile devices, tablet devices, onlineportals, ATMs, branches, call centers, sales forces, and so on. Each ofthese service group may receive and utilize data from IDP 2100 throughconnector grid 2110 a. Each channel may have a user interface designedto display various data and information and to receive user inputs.

Across channels 2300, customer information can be captured consistentlyat all points of collection for all LOBs and channels, aligned tostandards defined for the Enterprise Customer Domain. A single view ofcustomer information and aggregate view of customer holdings can bedisplayed on channels, in real-time or near real-time, and on demand ifnecessary.

In addition, product systems 2400 a, corporate systems 2400 b and T&Osystems 2400 c may also receive and utilize data from IDP 2100 throughconnector grids 2110 b, 2110 c.

IDP 2100 may receive raw data from a variety of data sources. Datasources include, among others:

-   -   Book of record transaction systems (BORTS)    -   Clickstreams (web-logs)    -   Social media    -   Server/machine logs    -   Unstructured data    -   Real-time event streams

Raw data may be received and stored into a staging area. The stagingarea may be part of a “data lake” foundation from which groups acrossthe organization can draw needed data. This staging area may be alsoreferred to as “level 0 (L0)” data storage.

For example, when the organization is a bank, different groups mayutilize data from the data lake. The groups may include: AML (Anti-MoneyLaundering), BOBS 239, Conditional Offer Pricing, Volcker, CCAR, FATCA,IFRS9, Stress Testing Model Development, Reg-W, Procure-to-Pay,Enterprise Customer Information (ECIF), Leads, Leads, TF, LRM/SMR, U.S.Heightened Standards, Enterprise Wire Payments, LOB (Line of Business)Scorecards, Corporate Audit Analytics, Fraud/Criminal RiskInvestigation, Legacy Data Marts Simplification.

IDP 2100 may be the foundation for the overarching data environment,combining multiple sources or book of record transaction systems (BORTS)into a single organization-wide repository and provides fast andcost-effective access to both raw and conformed data.

FIG. 1B is a view of components of a data storage and processing system.The system includes an integration component, data and analyticscomponent, and enterprise foundational components. The integrationcomponent has a connector grid. The connector grid provides enterpriseAPI services with standard interfaces to communicate with applicationsand external systems. The data and analytics component has aconsolidated Book of Record Data (BORT) and advanced analytics withmachine learning.

The enterprise foundational components include CIAM for identity andcredential management. CIAM enables single-sign on for data access withauthentication and authorization. The enterprise foundational componentsinclude Master Data Management components ECIF, RDM, and EPM to providea 360 degrees, holistic customer view of data. The Master DataManagement components have an enterprise product catalog. The MasterData Management components provide a single source of reference data.The enterprise foundational components include digitization and businessprocess management for digitization and document management with smartrobotics.

IDP 2100 integrates with digital document services to define and store,at the data hub, process pattern for digitization of documents. Theprocess patterns are re-usable. The process pattern indicate documentrequirements. Example requirements relate to document type or a numberof documents. The digital service receives a request to generate adocument package at the data hub, and the request can be linked to theprocess pattern. The linked process pattern defines parameters oroperations and requirements for the document package. The processpattern can be liked to a business function. For example, the processpattern can indicate requirements for documents associated with aspecific business function (e.g., mortgage application may require 5different documents) so that the digitization process can be automatedand a set of documents tracked as a package throughout its lifecycle,which can be integrated through a business process management (BPM)application to provide a repeatable and reusable business processpattern. The service can generate and store, at the data hub, thedocument package using a subset of data from the data at the data huband physical documents converted to electronic format according to theprocess pattern. The document package can stored at the data hub forsubsequent search and retrieval; and transmit the document package tothe target unit. In some embodiments, the process pattern is linked to abusiness function, domain or application. In some embodiments, theprocess pattern indicates a number of required documents for thedocument package. In some embodiments, the process pattern indicates atype of required document for the document package.

The document package can be associated with a document packageidentifier. The document services can be configured to monitor thedocument package at the data hub, detect a document change notification,and store the change notification in association with the documentpackage identifier as part of an audit log.

In some embodiments, the document services is configured to receive andstore a modified version of the document package containing at least oneelectronic signature in response to at least one electronic signaturerequest.

In some embodiments, the document services is configured to assign thedocument package to a user identifier having an access role, whereinprior to transmission, the document services is configured to check theaccess role and the target unit.

In some embodiments, the document package has at least one electronicsignature request. The service can detect a signature event at the datahub and capture data from the signature event for storage as part of thedocument package.

In some embodiments, the document services comprises an electronicsignature event listener to process the electronic signature event inreal-time.

In some embodiments, the document services comprises an electronicsignature event handler to receive the electronic signature events inreal-time from the electronic signature event listener.

In some embodiments, the processor integrates with one or more scannersto capture scanner data for the document package, the one or morescanners capturing the physical documents. The scanner data can providemetadata about the capture and also quality data.

FIG. 2 is a schematic diagram of an example architecture for adigitization and BPM services platform of IDP 2100 according to someembodiments. As depicted, the platform includes an enterprise servicegovernance unit and an API/service management unit, which connects toeach of a business services unit, customer identity access servicesunit, master data services unit, digitization services unit, andbusiness process management services unit, each of which connects to anadapter unit. The platform in turn connects to one or more of thefollowing: product systems, corporate systems, technology and operationssystems, and external systems. Each of these units can include therespective units as depicted.

The BPM services include process patterns to define re-usable processfor generating document packages. The process patterns can indicaterequirements for documents. Digitization can involve capturing orscanning physical documents and performing recognition operations (tocapture data form the document) for conversion into electronic documentsto be properly cataloged and filed into the enterprise documentrepository for subsequent search and retrieval. In addition, documentsassociated with a specific business function (e.g., mortgage applicationmay require multiple different documents) are automated tracked as adocument package throughout its lifecycle, which is often integratedthrough a business process management (BPM) application that forms arepeatable and reusable business process pattern. This is an examplebusiness process pattern that can be used for Branch Scanning. Anotherexample process pattern can be for Retail Branch service and productonboarding/account open process. The system can integrate the branchscanners which are informed by the document tracking services (builtwithin a storage integration layer) to scan a document packagedetermined by specific products/services onboarding BPM process. Suchprocess has been reused for Wealth Management branch business. Theprocesses can also be extended for business and commercial bankingbranch/office use case as well.

FIG. 3 is a schematic diagram of an example architecture fordigitization capabilities according to some embodiments. As depicted,digitization services can include scanning units, document recognitionand classification units, electronic signature units, faxing units,printing units, document generation units, document tracking units,digital library units, and documentation service (orchestration) units.The Document Tracking service enables signature-tracking in conjunctionwith document-acquisition tracking, and provides a single, accessible,point of reference for all document tracking capabilities through aConnector Grid service (Document Tracking Service). Document“Orchestration” refers to automated sequences of capabilities such asdocument generation, storage, electronic signing, etc.

As an example, in some embodiments, a digitization services platformimplements an improved document scanning system, for example, usable atbank branches. The digitization services platform automatically createsdocument packages and tracks them including eSigning. As with otherservices implemented by digitization services platform, this may providean audit trail that is as authentic, validated, and verifiable as apaper-based workflow. For example, the digitization services platformgenerates a form (e.g., paper or electronic) or request for initiationof a particular workflow. This may be a form that is to be physicallysigned by a user. The digitization services platform is then configuredto scan and receive the signed form or other indicia (e.g., electronicselection) that can be used by the platform to identify a particularworkflow. The digitization services platform is then configured toinitiate a particular workflow, for example, by OCR of the text orcontents of the signed form or the received indicia. For example, theindicia can be data indicating a mortgage application workflow isrequested. The digitization services platform includes an applicationthat generates a tracking service to track and determine the number andtype of documents needed for a particular workflow. The digitizationservices platform may then generate the appropriate data, for example,number and type of documents needed for that workflow and can providesame to the user. The digitization services platform is configured towait for receipt of completed or scanned versions of the completeddocuments and is configured to identify and wait for receipt of each andall of the documents determined to be required according to the workflowselected (e.g., mortgage application). For example, the digitizationservices platform may be configured to wait for seven documents of aparticular type to be scanned and received before moving to the nextstage of the workflow. In this example, the next stage of the workflowmay be the authorization of a mortgage.

In some embodiments, each stage is performed electronically, forexample, on an iPad. This can include the indication of the workflowrequested, signing of documents, and providing completed documents tothe digitization services platform. In each scenario in someembodiments, the digitization services platform is configured to trackall the documents needed for the workflow. In some embodiments, thedigitization services platform is configured to interoperate withexternal services such as those providing eSignature capabilities andsigning ceremony functionalities. In these situations, the digitizationservices platform is configured to pass control to the externalapplication for same to complete the signing ceremony and receivecontrol back from the external application once the signing ceremony hascompleted.

In some embodiments, the digitization services platform includes an OCRindex that can be used to tag documents with appropriate data attributesso as to be able to associate the document with particular data, forexample, with identifiers of a particular mortgage application orcustomer. Various document types may be accepted by the digitizationservices platform. This provides enhanced end to end digitizationservice capabilities. In this way, digitization services platform isconfigured to track all documents received and associate same with thecorrect context, for example, for later retrieval. This can improve oroptimize document retrieval time and allow for enhanced organization andaccess of documents relating to even other categorizations apart fromthe specific context the documents were received in. These attributescan also provide a feature set or a basis for extraction of a featureset for machine learning. Digitization services platform is configuredto interconnect with a machine learning unit, for example, included asanother component of the IDP that is configured to process, organize, orfacilitate understanding of the data.

In some embodiments, digitization services platform is configured toprovide service across an enterprise, including for different contextualenvironments and technical requirements associated with various lines ofbusiness, computer systems, services, channels, applications, andappliances within the enterprise. This may reduce or eliminate whatwould otherwise be a need for duplication of data and digitizationservice implementation. All channels, applications, and respective usecases may reuse these defined capabilities (e.g., form generation,rendering of a representation of a document to solicit data input from auser, etc.) of digitization services platform. For example, a particularuse case (e.g., mortgage application request) for a particular channelor application may engage with a selection of these definedcapabilities, with each other use cases engaging with different or thesame set of defined capabilities. This may also allow for improvedmaintenance and update processes of any component of the digitizationservices platform, as same can be updated once, with the updatedfeatures of the digitization services platform provided to allapplications and systems across the enterprise. In some embodiments,these changes are propagated to all or a selection of relevant channels,services, systems, and use cases.

In some embodiments, digitization services platform is configured toeliminate the need for scanning, with all documents provided, completed,signed, authenticated (e.g., identification of the user without scanningofficial identity documents) and received electronically, and, in someembodiments, partially or wholly in the background. Further, in someembodiments, digitization services platform is configured to improveform generation to support different configurations and use cases. Anexample form may be provided to a user to receive data that is used toinitiate the rendering of documents flexibly to receive further input.

In some embodiments, digitization services platform is configured togenerate and print a hard copy of documents, for example, copies of anagreement, at the end of the appropriate workflow.

In some embodiments, digitization services platform is integrated withrisk management platforms.

FIG. 4 depicts example business process management capabilitiesaccording to some embodiments. As depicted, the platform can include abusiness process management services unit, which can include a processmodelling unit, workflow execution unit, process performance managementunit, reusable process component units, dynamic resource assignmentunit, robotic automation unit, business rules unit, and digitizationintegration unit, with sub-units as depicted.

Digitization services can include document generation, capture, storage,and e-signature.

FIG. 5 depicts an example architecture for Digitization and BPM,according to some embodiments. FIG. 5 is intended to provide an examplecontext for the overall Digitization components. As depicted, adigitization process can flow through a number of various units withinstages such as channels; data, analytics, and services; functions; andproducts. The digitization process can include self-service (online), aswell as assisted (e.g., by bank branch employees) processes. Each stepis performed by units providing process automation, document capture,document generation, document storage, document viewing, eSignaturecapabilities, document indexing, and process status, as depicted.Customers can capture and upload documents, eSign documents, viewdocuments stored with the organization, trigger process flows as aresult of online applications, and see process flow statuses, forexample. Third parties can capture and upload documents, eSigndocuments, and view documents stored with the organization, for example.Faxed documents are indexed and stored in digital format in the digitallibrary.

FIG. 6 depicts an example schematic diagram of Document Managementimplemented by a digitization services platform, according to someembodiments. As depicted, a Hub can receive data, for example, from acentralized scanning unit, which can be provided to a digital libraryunit. The Hub can include one or more RightFax units, Captiva units,Connector Grids (including document tracking service), BPM servers,databases, SpotFire units, and Nimbus units, each interconnected asdepicted.

FIG. 7 is a schematic diagram of an example logical architecture for adistributed scanning service of a digitization services platform,according to some embodiments. As depicted, a Hub can include a digitallibrary unit, middle-ware unit, and a BPM server. The middle-ware unitcan include a document tracking service, document event service, anddocument service, as well as provide communication between the digitallibrary unit and BPM server, as depicted. An employee of theorganization can engage with a customer connect unit as well as abrowser. An MFD unit, for example, can upload scanned documents andmetadata to the digital library unit, via File Exchange Server. Data canflow through the depicted units sequentially according to the sequenceindicated by the reference letters.

FIG. 8 is a schematic diagram of an example logical architecture for adocument generation, e-Signature service of a digitization servicesplatform, according to some embodiments. As depicted, a user can view orsign documents or provided data to a signature unit. The user and/oremployee can engage with an eSignature App via a computing unit, aprivate wealth onboarding unit, customer connect unit, and onlinebanking unit. Each of these units can operate within one or more channelunits that interconnect with a Hub, for example, through an employeechannel services gateway. The Hub can interconnect with an enterprisebanking system unit. The Hub can include a digital library (DL) unit,document tracking service (DTS) unit, document service (DS) unit, andeSignature integration service (EIS) unit. The EBS unit can include asmart document set service (SDSS) unit and an eForms engine. Each ofthese units can interconnect with other units as depicted. For example,the DL unit can store unsigned documents from the DS unit. The DL unitcan retrieve unsigned documents from the EIS unit. The DL unit canreceive documents from the OLB unit and vice versa. The DS unit canupload data to the EIS unit. The DS and EIS units can interconnect toprovide document generation. The DTS unit can interconnect with thechannels unit to receive documents and document status changenotifications and vice versa.

FIG. 9 is a schematic diagram of an example Document Management ande-Signature key services of a digitization services platform, accordingto some embodiments. As depicted, the platform can receive a variety ofrequests. Each request can be managed by a respective service, forexample, documentation service, CCM service, CMISContent service, eSignservice, printer service, and document tracking service. Each servicecan be included within a connector grid unit. The CG unit (includingvarious sub-units that can house each service) can interconnect with anenterprise banking system unit, for example, for electronic formservices. The CG unit can also interconnect with a digital library. Suchinterconnection between any of these units can provide documentgeneration, document storage, and/or eSignature services as depicted.

FIG. 10 is a schematic diagram of BPM architecture as implemented by adigitization services platform, according to some embodiments. This caninclude Process Modelling, Execution, Performance Management, andRobotics. As depicted, the BPM architecture can include a workmanagement unit, process management unit, SOA integration unit, userinterface unit, modelling unit (for example, receiving data inputs frombusiness analysts, process developers, and SOA developers), and processvisibility unit.

FIG. 11 is an example flow chart of an example commercial lending dealcards scenario for process documentation using a digitization servicesplatform, according to some embodiments.

FIG. 12 is a schematic diagram of an example interface for adigitization services platform, according to some embodiments. Theinterface can provide Storyboards, which can provide a recorded guidedroute through a process, allowing users to follow a route or process.This can be used for communicating change, training, and best practices.This can provide a hhierarchal process definition with clearaccountability at each level, a user-friendly drawing tool to enablecollaboration between business experts and business analysts, arepository for process maps and related documentation, along with abrowser-based interface accessible by all stakeholders, an ability forprocess maps to be imported as a baseline flow for process developers,an ability for key performance indicator and service level agreementinformation to be added to focus process improvement efforts and guideusers for performance expectations, and support for governance forprocess maps.

FIG. 13 is a schematic diagram of an example process analysis for BPM.Digitization Services Platform can provide an interface to generate theexample depicted process schematics before and after scenarios toidentify ways to change or improve the process. This can also be usedfor costed processes to identify savings to be made by “Automating”activities to reduce manual intervention.

FIG. 14 is a schematic diagram of an example architecture for a BPM unitof a digitization services platform, according to some embodiments. Acustomer or third parties can provide data to a Hub, as depicted, forexample, to view, upload, or sign documents or to trigger process flows.The data can be received by a OLB unit or a Doc Portal unit, which canprovide data to a digital library unit included as part of a Hub. TheHub can also include a BPM server and Connector Grid and Sense andRespond units. Web services can provide an interface between the BPMserver and a product systems unit. An organization employee can engagewith an employee portal, which can provide eSign capabilities and canupload scanned documents and electronic documents and provide search,view, and upload capabilities through interconnection with the digitallibrary unit, as depicted. The various units can further interconnect toprovide the various features as depicted.

FIG. 15 is a flow diagram of an example process for integration usingBPM. As depicted, BPM sends a request to Connector Grid unit fordocuments to be scanned. BPM unit can also send a request to updateworkflow statuses at Connector Grid. Connector Grid can request aworkflow status at a customer unit. The customer unit can request aworkflow to be started at BPM unit. The customer unit can uploaddocuments and metadata to a digital library unit, which can also receivedocuments and metadata from a MFP unit, which can send scan requests andmetadata to the Connector Grid. The Connector Grid can include one ormore databases for storage of data.

FIG. 16 is a flow diagram of an example BPM process of key services fora digitization services platform, according to some embodiments. Asdepicted, a customer engages with a browser interface, which providesvarious functionalities such as application statuses, access to onlineapplications, and uploading documents. The browser interface isdisplayed through a device such as a mobile unit or tablet. The deviceprovides data to a Connector Grid unit, BPM unit, and FileNet unit asdepicted. Such data can be processed through respective web services andin response to various requests generated by respective units. Asdepicted, employees from various departments or lines of business withinthe organization can likewise engage with a browser to provide data tothe BPM unit. The BPM unit can open a checking account workflow or amortgage account workflow on request received a device receiving inputfrom a customer, for example. The BPM unit can also engage with aSpotfire unit. The FileNet unit can also engage with a document eventservice provided by a separate CG unit, for example. An MFP unit canprovide document and XML data to a File Exchange Server unit, which canprovide data to an audit unit, which can provide data to the FileNetunit.

In some embodiments, Workflow Initiation and Workflow Status servicesprovide an ability to launch workflows in BPM from channels (e.g.mobile, tablet) and/or an ability for customers to see workflow statuseswithin channel applications.

The abbreviations depicted in the figure have the following meanings:Workflow Initiation Service (WIS); Workflow Status Service (WSS);Document Service (DS); Document Event Service (DES); Document SetService (DSS); Document Tracking Service (DTS); and Content ManagementInteroperability Services (CMIS).

Examples of Process Performance Management using TIBCO Spotfire will nowbe described.

FIG. 17 is a chart depicting an example display for a volume monitoringprocess, according to some embodiments. The volume monitoring processcan include retrieving an application status at each step in theworkflow—e.g., Branch & Operations managers to monitor volume. This canbe configured to be viewed intraday (i.e. hourly) or daily, weekly,monthly intervals as required.

FIG. 18 is a schematic diagram of an example logical architecture forRobotic Process Automation, according to some embodiments. As depicted,the architecture includes a WorkFusion Platform, which a user device ororganizational system can provide input data to or otherwise engagewith. The WorkFusion Platform includes a load balancer, WorkFusionCluster unit (including one or more WorkFusion Applications), FileStorage unit, ML Cluster unit (including one or more machine learningunits), OCR Cluster unit (including one or more OCR units), databases,business intelligence servers, and application portfolio managementunits. The WorkFusion Cluster unit can interconnect with one or morerobotic process automation Clusters, including one or more RPA Servers,each of which can provide data (according to various protocols such asJDBC/ODBC; SOAP/HTTP; HTTP/S, etc.) to one or more of each oforganization databases, Connector Grid units, Web Applications, andDesktop Applications. The connector Grid unit can provide data to theorganization or a third party's Product Systems unit.

FIG. 19 is a schematic diagram of an example architecture implementingan eSignature (Assisted Channel) use case for a digitization servicesplatform, according to some embodiments. The architecture can include anEmployee Portal unit, signature unit, and IDP. The IDP can include a CGunit, Digital Library unit, and CCM/eForm unit. Each of these units caninterconnect as depicted to provide the various depicted functionalitiesusing the various depicted protocols and sequences.

FIG. 20 is a schematic diagram of an example architecture implementingan eSignature (Online Channels) use case for a digitization servicesplatform, according to some embodiments. Specifically, depicted is aDigital Channel using the CCM Service and eSignature Service as twodistinct web-services (and two invocations). The Documentation Serviceallows channel applications, BPM, etc. to generate documents needed fora particular product as well as initiate e-Signature for relevantdocuments in a single web-service call. The “one-stop shop”Documentation Service, however, might not be reusable (or desired) inparticular use-cases, in which case the CCM and ESign Services can beutilized as “standalone” services, as depicted here. The architecturecan include an signature unit, Digital Channel unit, and SmartCore,which can include one or more CG units, a Digital Library, and aCCM/eForm unit.

FIG. 21 is a schematic diagram of an example architecture implementingEvent Handling for an e-Signature functionality. As depicted, theplatform can include a CG unit, with the various depicted handlers. Eachhandler can provide event data to one or more external units, asdepicted. The CG unit can also create an eSign package using a specificaccount and provide same to an external signature unit using aREST/HTTPs protocol. The signature unit can provide eSign Events to anevent servlet to provide same to an event distributor unit included aspart of the CG unit.

Example embodiments of Hub E-Forms and ESign Services as part of a Hubwill now be described in further detail.

Enterprise Core Standards can include a Document Management ProductStandard (STD-0081-01) and a Hub SOAP Message Format (STD-0105-01).

Embodiments described can provide e-Signature Services that supportenterprise-wide reuse.

In some embodiments, there may be a set of electronic forms, a CustomerCommunication Management (CCM), “eForms” platform and e-Signatureplatform along with channel interaction.

FIG. 22 is a schematic diagram of an example state of an e-Signaturearchitecture, according to some embodiments. As depicted, the platformcan receive data via a variety of respective services and can include aCG unit and various other units.

FIG. 23 is a schematic diagram of an example state of an e-Signaturearchitecture, according to some embodiments. As depicted, the platformcan receive data via a variety of respective services from a corporateservices unit.

Other service, such as the Document Event Service (DES), EmployeeNotification Service, play a part in the overall eForms and e-Signatureimplementation, but have been omitted from this diagram. In addition,existing services supporting Branch Scanning, though used by eForms ande-Signature services, are not displayed. The EICEmployee service is alsonot depicted.

FIG. 24 depicts an example architecture for an eSignature Service(Assisted Channel, ESign and CCM Services). Specifically, there isdepicted an Employee Portal (e.g. Customer Connect) using the CCMService and eSignature Service as two distinct web-services (and twoinvocations).

The context of an example Documentation Service according to someembodiments of a digitization services platform is to provide a“one-stop shop” service to channels, allowing documents to be generated,stored in the Digital Library, and submitted for electronic signature.

The scope includes a GenerateAndESign unit, which generates documentsassociated with a specified product, stores the unsigned documents inthe Digital Library, and submits documents to be e-signed for electronicsigning; a GenerateAndPrint unit, which generates documents associatedwith a specified product, stores the unsigned documents in the DigitalLibrary, and sends documents to be “paper” signed to a network-attachedprinter for printing; a Reassign Packages unit, which reassignsDocumentTrackingService (DTS) document packages from one employee toanother; and a RemovePackages unit, which removes the specifiedDocumentTrackingService (DTS) document packages, along with any e-Signpackages that may exist.

The context of an example Customer Communication Management (CCM)(“Document Generation”) Service according to some embodiments of adigitization services platform is to provide the means for applications(such as Customer Connect, the Digital Channel, BPM, etc.) to generatedocuments (typically output as PDFs), returning generated documents tothe caller and/or storing them in the Digital Library and/or placingthem into a user-specified output folder.

The scope includes a Generate Documents unit, which can generate one ormore documents, either returning them to the caller (as attachments), orstoring them in the Digital Library or a caller-specified output folder.

The context of an example Document Tracking Service according to someembodiments of a digitization services platform is to provide an abilityto track acquisition, scanning and/or electronic signing of documents,as well as state management and query capabilities.

The platform includes an AddPackagesToPendingPackages unit, whichchanges the status of document packages to “pending”; aQueryMyPendingPackages unit, which allows a caller to query pendingdocument packages; and a RemovePackagesFromPendingPackages unit, whichremoves the specified packages from the pending state.

FIG. 25 is a schematic diagram of an example architecture for ComponentInteraction between ESign Service, Handlers, and Document Trackingservices. The diagram provides a component-interaction view of the ESignand Document Tracking services, and ESignEvents handler.

In some embodiments, there is provided a Documentation Service, whichcan interconnect with various components.

Embodiments described herein can provide operational logging andauditing services.

FIG. 25 is a schematic diagram depicting some embodiments where Hubservices involved in eForms are e-Sign processing can log componenthealth and transaction processing to support operational monitoring.

In addition, as depicted, access to documents stored in the DigitalLibrary (whether by customers via OLB, or by employees via the UI and/orCustomer Connect) is to be recorded for audit purposes. This may be thatthe CMISContent adapter produce an audit log of customer access todocuments, and that the Digital Library produce and audit log ofemployee document access.

FIG. 26 is a schematic diagram of an example architecture for an AuditLogging and Reporting service of a digitization services platform,according to some embodiments. In some embodiments, content managementservice will log the certain data elements for audit reporting relatingto customer document accesses; content management service can log theProxy ID of the customer user accessing documents from the DigitalLibrary; the Digital Library can log the user IDs of employee useraccess; the Digital Library can log the user accesses for customers;Customer and Employee user access logs are shipped to IDP; and reportscan be created to allow audit users to view DL document accessactivities by customers or employees.

The architecture can include logging accesses to documents in a DigitalLibrary, as well as enabling an audit team to review reports.

This table summarizes some significant architectural and managementdecisions that may be involved in the design of the architecture.

In some embodiments, adds, changes and deletes to the data can bemonitored.

Functions and applications can be changed in any one of the followingways: connection to the HUB via an adaptor; consumption of CIFinformation from MDM/HUB; consumption Analytic information from HUBand/or Virtual EDW; migration of orchestration to the HUB; migration ofbusiness logic to the HUB; migration of presentation logic to the HUB;and movement to strategic standards from non-strategic standards(includes platforms).

According to some embodiments, the following table summarizessystem-to-system interfaces between components.

Source Destination Protocol Sync/Async Notes Browser ESign Service HTTPSSynchronous Browser-based UI BPM ESign Service SOAP/ SynchronousWorkflows running on BPM can HTTPS create eSign packages, add documentsto a package (by specifying FileNet URLs), and invite customers to sign.Customer ESign Service SOAP/ Synchronous The Digital Channel andConnect, HTTPS Customer Connect can create Digital Channel eSignpackages, add documents to a package (either existing documents storedin database, or newly generated documents directly uploaded to theeSignature Service), invite customers to sign, and start an e-signsession. ESign Service ESign Service REST/ Synchronous The ESign Serviceuses a HTTPS signature API ESign Service Digital Library SOAP/Synchronous The ESign Service uses the HTTPS CMISAdapter retrievedocuments (before uploading them for signing), and to store e- signeddocument/s. signature e-Sign Event JSON/ Synchronous Signing events aredelivered to process Listener HTTPS the eSignature Event Listener usingHTTP POSTs sent to an HTTPS endpoint (the eSignature Event “Listener”).The URL can include a shared key. Each HTTP POST carries the shared key,allowing the Event Listener to validate the origin of the events.eSignature ESignEvents JSON/ Synchronous Events received by the EventListener Handler HTTPS eSignature Event Listener are passed to theConnector Grid's eSignature Event Handler via HTTP POST, whichdistributes the events to interested parties as needed. ESignEventsESign Service REST/ Synchronous When a ‘package complete’ Handler HTTPSevent is received by the ESignEvents Handler, the handler notifies theESign Service, which retrieves the signed document/s and stores them.ESign Service Digital Library SOAP/ Asynchronous After downloadingsigned HTTPS document/s, the eSignature Event Handler stores thedocuments. ESign Service “Drop folder” SFTP Asynchronous If signeddocuments are not stored, then ESign Service can deliver the signeddocuments to a “drop folder” (specified at the time the e-sign packagewas created). ESignEvents “Callback” XML/ Asynchronous Signing eventsreceived by the Handler queue/topic JMS ESignEvents Handler posted tothe “callback” queue or topic provided at the time that the e- signpackage was created. ESignEvents Document SOAP/ Synchronous When signingevents containing Handler Tracking HTTPS a DTS packageID and Service(DTS) documentID are received, the Event Handler invokesupdateDocumentStatus(SIGNED) on the Document Tracking Service. CustomerEICEmployee SOAP/ Synchronous Get employee information (i.e. ConnectService HTTPS job role, etc.).

FIG. 27 is a schematic diagram of an example process for e-Signingdocuments online (via a Digital channel-initiated e-Sign session),according to some embodiments. As depicted, data can flow through abrowser unit, digital channel unit, Doc-Gen service (CG) unit, doctracking service (CG) unit, eForm engine, eSign service (CG), eSignevent listener (DMZ), eSign event handler (CG), digital library unit,and DES unit.

In some embodiments, the following services are authenticated usingSPNEGO (via DataPower): CMISContent, documentation,DocumentTrackingService, eSign, and printer.

In these embodiments, these services are exposed to channel applicationsas SOAP/HTTPS endpoints.

The following table describes features of an example digitizationservices platform, according to some embodiments.

Quality Attribute Definition Specifications and solution AvailabilityThe ability of the system Continuous: The system can be that representsa measure continuously available to users, Monday of its readiness forusage through Sunday, 365 days a year, (e.g., Hours of operations)excluding scheduled maintenance. Scheduled maintenance will be definedin the Operational Level Agreement. Application and infrastructurecomponents are designed to allow for ‘continuous’ availability. Disasterrecovery component should be available with recovery time object of 4hours DR components are integrated into the application andinfrastructure design Reliability The ability of the system to Minoroutage - Up to 15 minutes keep operating over time. Major outage - up to1 hour Reliability is usually Critical outage - >1 hour measured by meantime to ‘Continuous’ availability is designed into failure (% downtime).the application and infrastructure design Performance The responsivenessof the Online Response time system - that is, the time Capacity planningis based on the that may be used to performance criteria. Performancetesting respond to stimuli (events) is part of the development process.or the number of events processed in some interval of time. Oftenexpressed by the number of transactions per unit time, or by the amountof time that it takes to complete a transaction with the system (e.g.,Transaction latency and volume, Peek performance characteristics).Scalability The ability to maintain or Time frame: 5 years. Organicgrowth improve performance while expectation - 10% increase in customerssystem demand increases and their transaction (e.g., transaction volumeThe application and infrastructure design growth). allow scalingvertically and horizontally for the organic & planned growth Security Ameasure of the system's SSL (HTTPS) between browser. ability to resistSSL mutual-auth between BPM and CG, unauthorized attempts at viaDataPower. usage and denial of FileNet uses standard AD-based loginsservice, while still providing and SSL. its services to legitimateusers. Security is categorized in terms of the types of threats thatmight be made to the system. Maintainability The aptitude of a system toAll changes will be handled through the undergo repair and ProductionChange Process. evolution. Allow Operations to move an application (1)The ease with which a from one server to another, independent softwaresystem or of any other application, and without component can beapplication code changes. modified to correct faults, Design to enablerolling upgrades/ improve performance or staged implementation. otherattributes, or adapt to a changed environment. (2) The ease with which ahardware system or component can be retained in, or restored to, a statein which it can perform functions. Supportability The ease with which aApplication and infrastructure software system can be componentssupports EI standard operationally maintained. monitoring tools. Willdeploy EI standard monitoring tools; TIVOLI, BMC, Intrascope, etc.).Reusability The degree to which a Solution uses the HUB shared servicessoftware module or other (BPM and FileNet). work product can be used inmore than one computing program or software system. This is typically inthe form of reusing software that is an encapsulated unit offunctionality. Extensibility Description on how The HUB services arearchitected to architecture support enterprise extensibilityaccommodates future changes.

The following table describes mapping between application components andvarious components of a digitization services platform, according tosome embodiments.

Application/Solution Components/Services Platform Gateway Data PowerDocumentation Service CG Document Tracking Service CG Document EventService CG Smart DSS EBS - Java on WAS (Liberty Base EmployeeNotification CG (EMS Topic) Documents Operational IDP and SpotfireReports Printer Service CG CMISContent CG EICEmployee CG BPM Hub BPM

In some embodiments of digitization services platform, the followingprocess digitization core areas can have a variety of technologystandards and example states and alignment: scanning, documentmanagement, workflow, e-Signature, search, specialized workflows.

For example, various technology standards are provided for processdigitization services, according to some embodiments.

Category Description Process Documentation Document and analyze businessprocesses; make process documentation available to employees. Fax Sendand receive electronic faxes Capture & Scanning Convert paper toelectronic format (Scan, Fax), including extraction of metadata andother info from scanned documents or images (such as TIFF files fromreceived faxes) using OCR, bar-code reading, etc. and ingest captureddocuments into Content Management system. Archive/Document ManagementProvide storage, search and retrieval for electronic documents-typicallythose associated with customer- related activities (e.g. loanapplications, proof of employment, income verification)-as well asmanage document lifecycle (e.g. records management) Workflow Automatebusiness processes and provide insight into process performance,cycle-times, etc. allowing for continual process improvement/refinement.e-Signature Allow customers and employees to electronically affix asignature or its equivalent to an electronic document, both online(“unmediated signing”¹) and person (“mediated”¹, in-branch, forexample). Search Search for (electronic) documents based on user-enteredsearch criteria. Currently search is limited to documents stored inFileNet, but future capabilities July extend search across Sharepoint,LiveLink, etc. Collaboration Enable internal (employee-to-employee) andexternal (employee-to-customer) collaboration and document sharing.Specialized Workflows

There may be provided mediated or unmediated e-signing.

In some embodiments, various specialized workflows are provided ortechnology standards used for process digitization services.

“Specialized workflows” refers to use-cases where workflow functionalityis used, and such “workflow” functionality might already exist within anoff-the-shelf product being considered, or a strong case can be made touse an alternative to the organization's workflow standard (e.g., BPM).

In general, for new “specialized workflows” BPM should be considered foruse. Where workflows need to span both front-office (branch) and productoperations, BPM provides strong support.

Each new “specialized workflow” should be considered on a case-by-casebasis using the standard Hub Intake process.

Migration of existing “specialized workflows” to BPM should beconsidered as/when business process improvement is desired.

FIG. 28 is a schematic diagram of example capabilities and vendors forprocess digitization services, according to some embodiments.

The following table summarizes example capabilities for processdigitization services, according to some embodiments.

Capability Process Documentation Fax Scan & Capture Archive/DocumentManagement Record Management (associated with Archive/Doc Mgmt)“Workflow” eSignature Search Collaboration

The following table describes various standards used for thebelow-listed use cases, according to some embodiments.

Use-case P&C Product Operations “Workflow” Customer Onboarding P&CMortgage Workflow US AML High-Risk Unit (HRU) Workflow P&C CommercialLending Workflow (“specialized workflow”)

The diagram shows the established integration between key components ofthe Hub's Digitization Foundation, for example RightFax, Captiva,Digital Library, and BPM. For example, for RightFax, faxes received byRightFax are routed for image quality improvement and indexing. Forfaxes, scanned documents that are processed (image quality checks,enhancement, indexing) are, among other paths, routed into the DigitalLibrary for storage and subsequent retrieval. For the Digital Library,the Digital Library has been integrated (via Connector Grid) with:branch-scanning solutions (allowing scanned documents to be directlyuploaded and stored); BPM, sending notifications to workflows whendocuments are stored/updated, allowing workflows to automatically moveon to the next step in the workflow (typically a “Review documentsstep”); and end-user applications, allowing employees to search fordocuments stored in the Digital Library, update document metadata, etc.directly from familiar applications (such as Customer Connect, BPMworkspace, etc.).

For BPM, for Branch Scanning services, BPM is integrated with the branchscanning solution, allowing workflows to request documents to bescanned, and employees to use in-branch MFDs to scan documents directlyinto the workflow. BPM is tightly integrated with Spotfire, allowingprocess cycle times, etc. to be visualized, and enabling continualprocess improvement.

The diagram shows an example state of the organization's ProcessDigitization technology stack. Key points are the addition ofe-Signature services (both in-branch and online); ability for customersto upload documents from online channels (shown as “OLB” in thediagram); and ability to launch workflows in BPM from channels (e.g.mobile, tablet).

The diagram shows a view of the target state of the organization'sProcess Digitization technology stack. Key points are an ability forcustomers to upload documents from online channels (shown as “OLB” inthe diagram); an ability to launch workflows in BPM from channels (e.g.mobile, tablet); ability for customers to see workflow status withinchannel applications; and automated workflow spanning front-office andproduct operations.

The diagram depicts a variety of services indicated by the followingabbreviations: WIS (Workflow Initiation Service); WSS (Workflow StatusService); DS (Document Service); DES (Document Event Service); DSS(Document Set Service); DTS (Document Tracking Service); and CMIS(Content Management Interoperability Services).

In cases where business processes are automated by means of BPM-drivenworkflows, a “structured” approach can be taken to getting the requireddocuments into the Digital Library, as depicted. For example, a customercompleting an online application from a tablet, PC, etc. (a) for someproduct might, behind the scenes, give rise to new workflow in BPM (b).When documents are required, the workflow in BPM can submit a requestfor documents to be scanned (by an employee) or uploaded (by acustomer), or possibly both. Employees can then scan documents (eitherinternally generated or brought in by a customer) at a Multi-FunctionPrinter (MFP) (c), and/or customers can upload documents from onlinechannels. Either way, the documents are stored in the Digital Library(d). This process is referred to as “structured” document acquisition.

In cases where business processes are fluid, or not automated byBPM-driven workflows, an “informal” or ad hoc approach can be taken tosharing documents with, or obtaining documents from customers. Thisprovides a second implementation of collaboration services(“Informal”/Ad Hoc Document Acquisition/Sharing).

For example, when sharing files with customers, using OneDrive,employees can share files with customers, and customers can then accessthose files via the Internet (by logging into OneDrive). When receivingfiles from customers, employees can share folders with customers,granting individual customers “write” access, allowing the customer toupload files into the shared folder in the employee's OneDrive account.Uploaded files are automatically “synced” to the employees workdevice(s) and can be accessed.

The embodiments of the devices, systems and methods described herein maybe implemented in a combination of both hardware and software. Theseembodiments may be implemented on programmable computers, each computerincluding at least one processor, a data storage system (includingvolatile memory or non-volatile memory or other data storage elements ora combination thereof), and at least one communication interface.

Program code is applied to input data to perform the functions describedherein and to generate output information. The output information isapplied to one or more output devices. In some embodiments, thecommunication interface may be a network communication interface. Inembodiments in which elements may be combined, the communicationinterface may be a software communication interface, such as those forinter-process communication. In still other embodiments, there may be acombination of communication interfaces implemented as hardware,software, and combination thereof.

Throughout the foregoing discussion, numerous references will be maderegarding servers, services, interfaces, portals, platforms, or othersystems formed from computing devices. It should be appreciated that theuse of such terms is deemed to represent one or more computing deviceshaving at least one processor configured to execute softwareinstructions stored on a computer readable tangible, non-transitorymedium. For example, a server can include one or more computersoperating as a web server, database server, or other type of computerserver in a manner to fulfill described roles, responsibilities, orfunctions.

The foregoing discussion provides many example embodiments. Althougheach embodiment represents a single combination of inventive elements,other examples may include all possible combinations of the disclosedelements. Thus if one embodiment comprises elements A, B, and C, and asecond embodiment comprises elements B and D, other remainingcombinations of A, B, C, or D, may also be used.

The term “connected” or “coupled to” may include both direct coupling(in which two elements that are coupled to each other contact eachother) and indirect coupling (in which at least one additional elementis located between the two elements).

The technical solution of embodiments may be in the form of a softwareproduct. The software product may be stored in a non-volatile ornon-transitory storage medium, which can be a compact disk read-onlymemory (CD-ROM), a USB flash disk, or a removable hard disk. Thesoftware product includes a number of instructions that enable acomputer device (personal computer, server, or network device) toexecute the methods provided by the embodiments.

The embodiments described herein are implemented by physical computerhardware, including computing devices, servers, receivers, transmitters,processors, memory, displays, and networks. The embodiments describedherein provide useful physical machines and particularly configuredcomputer hardware arrangements. The embodiments described herein aredirected to electronic machines and methods implemented by electronicmachines adapted for processing and transforming electromagnetic signalswhich represent various types of information. The embodiments describedherein pervasively and integrally relate to machines, and their uses;and the embodiments described herein have no meaning or practicalapplicability outside their use with computer hardware, machines, andvarious hardware components. Substituting the physical hardwareparticularly configured to implement various acts for non-physicalhardware, using mental steps for example, may substantially affect theway the embodiments work. Such computer hardware limitations are clearlyessential elements of the embodiments described herein, and they cannotbe omitted or substituted for mental means without having a materialeffect on the operation and structure of the embodiments describedherein. The computer hardware is essential to implement the variousembodiments described herein and is not merely used to perform stepsexpeditiously and in an efficient manner.

For simplicity only one computing device 2100 is shown in FIG. 2, butthe respective systems may include more computing devices operable byusers to access remote network resources and exchange data. Thecomputing devices may be the same or different types of devices. Thecomputing device includes at least one processor, a data storage device(including volatile memory or non-volatile memory or other data storageelements or a combination thereof), and at least one communicationinterface. The computing device components may be connected in variousways including directly coupled, indirectly coupled via a network, anddistributed over a wide geographic area and connected via a network(which may be referred to as “cloud computing”).

Although the embodiments have been described in detail, it should beunderstood that various changes, substitutions and alterations can bemade herein.

Moreover, the scope of the present application is not intended to belimited to the particular embodiments of the process, machine,manufacture, composition of matter, means, methods and steps describedin the specification. As one of ordinary skill in the art will readilyappreciate from the disclosure of the present invention, processes,machines, manufacture, compositions of matter, means, methods, or steps,presently existing or later to be developed, that perform substantiallythe same function or achieve substantially the same result as thecorresponding embodiments described herein may be utilized. Accordingly,the appended claims are intended to include within their scope suchprocesses, machines, manufacture, compositions of matter, means,methods, or steps.

As can be understood, the examples described above and illustrated areintended to be exemplary only.

What is claimed is:
 1. A system for digital document services,comprising at least a processor and a non-transient data memory storage,the data memory storage containing machine-readable instructions forexecution by the processor, the machine-readable instructions configuredto, when executed by the processor, provide a document serviceconfigured to: load and store data from a plurality of source systems ata data hub implemented by a non-transient data store; define and store,at the data hub, process pattern for digitization of documents, theprocess pattern indicating document types; receive a request to generatea document package at the data hub, the request indicating a targetunit, the request linked to the process pattern; generate and store, atthe data hub, the document package using a subset of data from the dataat the data hub and physical documents converted to electronic formataccording to the process pattern, the document package stored at thedata hub for subsequent search and retrieval; and transmit the documentpackage to the target unit.
 2. The system of claim 1, wherein thedocument package is associated with a document package identifier,wherein the document services is configured to monitor the documentpackage at the data hub, detect a document change notification, andstore the change notification in association with the document packageidentifier as part of an audit log.
 3. The system of claim 1, whereinthe document services is configured to receive and store a modifiedversion of the document package containing at least one electronicsignature in response to at least one electronic signature request. 4.The system of claim 1, wherein the document services is configured toassign the document package to a user identifier having an access role,wherein prior to transmission, the document services is configured tocheck the access role and the target unit.
 5. The system of claim 1,wherein the document package has at least one electronic signaturerequest and wherein the processor can detect a signature event at thedata hub and capture data from the signature event for storage as partof the document package.
 6. The system of claim 5, wherein the documentservices comprises an electronic signature event listener to process theelectronic signature event in real-time.
 7. The system of claim 6,wherein the document services comprises an electronic signature eventhandler to receive the electronic signature events in real-time from theelectronic signature event listener.
 8. The system of claim 1 whereinthe process pattern is linked to a business function, domain orapplication.
 9. The system of claim 1 wherein the process patternindicates a number of required documents for the document package. 10.The system of claim 1 wherein the process pattern indicates a type ofrequired document for the document package.
 11. The system of claim 1wherein the processor integrates with one or more scanners to capturescanner data for the document package, the one or more scannerscapturing the physical documents.
 12. A non-transitory machine-readablemedium storing instructions configured to, when executed by theprocessor, provide a digitization service configured to: define andstore, at a data hub, process pattern for digitization of documents, theprocess pattern indicating document types, the data hub storing datafrom a plurality of source systems, the data hub implemented by anon-transient data store; receive a request to generate a documentpackage at the data hub, the request indicating a target unit, therequest linked to the process pattern; generate and store, at the datahub, the document package using a subset of data from the data at thedata hub and physical documents converted to electronic format accordingto the process pattern, the document package stored at the data hub forsubsequent search and retrieval; and transmit the document package tothe target unit.
 13. The machine-readable medium of claim 12, whereinthe document package is associated with a document package identifier,wherein the document services is configured to monitor the documentpackage at the data hub, detect a document change notification, andstore the change notification in association with the document packageidentifier as part of an audit log.
 14. The machine-readable medium ofclaim 12, wherein the digitization services is configured to receive andstore a modified version of the document package containing at least oneelectronic signature in response to at least one electronic signaturerequest.
 15. The machine-readable medium of claim 12, wherein thedocument services is configured to assign the document package to a useridentifier having an access role, wherein prior to transmission, thedocument services is configured to check the access role and the targetunit.
 16. The machine-readable medium of claim 12, wherein the documentpackage has at least one electronic signature request and wherein theprocessor can detect a signature event at the data hub and capture datafrom the signature event for storage as part of the document package.17. The machine-readable medium of claim 16, wherein the documentservices comprises an electronic signature event listener to process theelectronic signature event in real-time.
 18. The machine-readable mediumof claim 17, wherein the document services comprises an electronicsignature event handler to receive the electronic signature events inreal-time from the electronic signature event listener.
 19. Themachine-readable medium of claim 12 wherein the process pattern islinked to a business function, domain or application.
 20. Themachine-readable medium of claim 12 wherein the process patternindicates a number of required documents for the document package. 21.The machine-readable medium of claim 12 wherein the process patternindicates a type of required document for the document package.
 22. Themachine-readable medium of claim 12 wherein the processor integrateswith one or more scanners to capture scanner data for the documentpackage, the one or more scanners capturing the physical documents.